Columbia Kermit/kermit.zip/newsgroups/misc.19941031-19941221/[e-mail]_Wed Dec 14 04:08:17 1994.msg

Internet Message Format | 2020-01-01 | 4KB

Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA21682
  (5.65c+CU/IDA-1.4.4/HLK for <[e-mail]>); Sat, 17 Dec 1994 04:26:23 -0500
Received: by apakabar.cc.columbia.edu id AA02525
  (5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Sat, 17 Dec 1994 04:26:21 -0500
Path: news.columbia.edu!spcuna!solaris.cc.vt.edu!news.mathworks.com!europa.eng.gtefsd.com!gatech!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: [e-mail] (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: 3.14 beta 14 and PC/TCP
Message-Id: <[e-mail]>
Date: 14 Dec 94 10:08:17 MDT
References: <[e-mail]> <[e-mail]> <[e-mail]>
Organization: Utah State University
Lines: 53
Apparently-To: [e-mail]

In article <[e-mail]>, [e-mail] (Jamie Watson) writes:
> In article <[e-mail]> [e-mail] (Joe Doupnik) writes:
>>    The situation is easy to clarify. SET PORT TCP in Kermit means
>>to use Kermit's internal TCP/IP stack. That stack requires either a suitable
>>Packet Driver or ODI to talk to the lan adapter. FTP Inc's stack does more
>>or less the same thing. You loaded FTP Inc's stack and then told Kermit to
>>go to the same board and grab it; you are not running "over FTP Inc's stack."
>>I'm surprized that you we able to run Kermit over the board with FTP still
>>using all the TCP/IP material.
>
> Sigh.  I'm really sorry for having asked such a bonehead question.  I read
> about this restriction in several different places, but I am obviously
> not knowledgeable enough about DOS and networking to have understood what
> it really meant.  I had assumed that it meant that I couldn't run kermit
> and one of the PC/TCP utilities at the same time, but now that I stop to
> think about that, it's a pretty silly idea under DOS; I guess it just
> shows that my mind has frozen into Unix-based thought patterns.  Anyway,
> I just tried unloading the PC/TCP stack (inet unload) before starting
> kermit, and then reloading it (ethdrv) after terminating kermit, and it
> works just fine.  Thanks for the help.
>
>>    If you want FTP Inc's stack to remain resident and run Kermit
>>over the top of it you must use FTP's TNGLASS program, and tell Kermit
>>SET PORT BIOS1.
>
> This still doesn't work for me, even with Beta-15 installed.  I first
> tried just "tnglass pan", and it connects just fine.  I then tried the
> command specified in networks/setup.doc, and found that I had to change
> the argument format somewhat to even get it to accept the command, but
> it still doesn't work.  The command I gave was:
>
>     tnglass pan -c 0 -i -e kermit.exe set port bios1 , connect
>
> This starts the tnglass program, and then starts kermit, but it immediately
> says "Connection closed".  I have tried just starting kermit without the
> commands on the command line, then given the bios1 and conect to kermit
> myself, but I got the same result.  Am I still doing something wrong?  By
> the way, I am using PC/TCP version 3.0, so that might explain at least the
> difference in command line parsing; I assume that the setup.doc file was
> written based on PC/TCP version 2.3 or earlier.
---------------
    Works here, but without the "-i" option. That option is supposed
to keep the Telnet session open until the external terminal emulator loads
(which makes sense, but why would we need a option for something as necessary
as this?), and <something, antecedent unclear in the manual> sends an Int 14h
init command.
    If I include the -i option then the connection is closed by the
time the terminal emulation screen comes up, else it stays open. Go figure.
    The same thing happens with MSK 3.13.
    Please follow directions from the vendor of the product you are
using. For Tnglass follow those of FTP Software Inc for tnglass options
of the version you have.
    Joe D.